UMBRAPHILE has gone native.
Intel MacOS X native, that
is.
It only took my last Mac laptop, a 2003 epoch Powerbook
capable of running the MacOS 9 “classic” emulator, going belly up
(fried CPU board) to motivate me sufficiently to invest the to
bring UMBRAPHILE into the 21st century. A BETA release that has
been tested for MacOS through 10.4.11 (I haven't myself gone to 10.5
yet) is available for download on my web site for others to use for
automated eclipse imaging here:
DOWNLOAD the most recent version of UMBRAPHILEX (.zip
file) from this directory:
http://nicmosis.as.arizona.edu:8000/ECLIPSE_WEB/UMBRAPHILE/UMBRAPHILEX/
The "Classic" UMBRAPHILE page describes and details the basic use and
functionality of the application.
I have
closely replicated the flavor, feel and functionality, of the "Classic"
UMBRAPHILE in the (Intel) MacOS X version. Anyone with
an Intel-base Mac laptop who may want to consider automating their
eclipse photography can download the beta version and get back to me
with comments, problems, suggestions, etc. I am not sure how much
I can get done before TSE 2008, but let me know, as I am keeping a list
for TSE2009. The classic version of the S/W (most recent 2006 B) still
work pre-Intel Macs with classic (Mac OS 9) environments. A an
UMBRAPHILE data file for TSE 2008 can be downloaded on the UMBRAPHILE
2006B page. At this juncture, all future development for
UMBRAPHILE will be for MacOS X machines. "Classic" users (native
or in a classic shell in MAc OS X on those machines which support that)
can continue to use the 2006 B version of UMBRAPHILE.
With UMBRAPHILE X, you will find lots of little things that are a bit
different. I
mention just the important ones here so anyone interested can
understand how to get it up and running with their camera
interface. The primary camera interface philosophy remains
unchanged. I.e., to drive the shutter control line of any camera
with
an electronic/electrical shutter interface you will need to build a
SIMPLE circuit such as shown on the above referenced web page.
That circuit needs to be hooked up to a MacOS X computer through a
USB-to-serial port converter, such as the Keyspan Twin Serial Adapter
USA-28XB (that is the one I use, but other similar ones should work)
plugged into a USB port… and the driver for the adapter
installed.
Keyspan’s drivers are here: http://www.keyspan.com/downloads .
USB-to-Serial adapters made by other vendors may also work (I just do
not have first-hand experience with them).
NOW… Here are main the differences:
1. USB-to-Serial Port Device
Adapter Name
With the adapter plugged in, you need to tell UMBRAPHILE the
name of the USB-to-Serial adapter device you are using. The
device (adapter) will automatically “register” itself within
the MacOS X when plugged in, but UMBRAPHILE won't know what device that
i until you tell it. There is a new Umbraphile menu item to SET
USB PORT to do that. The simplest way to get the name of the
device (once it is plugged in) is to open a terminal window (e.g.,
launch the Terminal application from the Mac finder) and type the unix
command: ls /dev
You will see a long list of terminal "tty", "pty" and other device
names. If you
are using a Keyspan 28X adapter look for a name (or names if a
multi-port adapter) like: tty.USA28X3d1P1.1
The numbers may be different but should be easy to spot. This is
the name you need to specify in the Umbraphile SET USB PORT dialog
box. When you do that you ned to prefix that with
/dev/ so what you enter is, for example: /dev/tty.USA28X3d1P1.1
. There is a default device name in the dialog (to show you the
syntax) that you can need to edit with the name of your device or
Umbraphile wont be able to talk to your
camera(s)). NOTE: One UMBRAPHILE user (Joel Moskowitz) reports
that with his different model USB-to-Serial port converter, when the
device is plugged in, it registers port names with both a "cu" and
"tty" prefix; and only the "cu.PORTNAME" device works - and the
tty.PORTNAME device (which also shows up in /dev) will cause
UMBRAPHILEX to "hang". I have no "fix" for that. If you
give an incorrect port name (that is not in /dev) UMBRAPHILEX will let
you know - but if you give the name of a port that does not function as
UMBRAPHILE expects it may hand the application, and you will need to
"Force Quit" from the MacOS Finder and try the "other" port name (if
more than one).
2. If You Need to Change the
Adapter Device Defaults
The USB-to-Serial adapter port must be set for 9600 Baud
communication. By default (if you are using a Keyspan device ) it
should probably come up that way when plugged in. You
can check by typing the following unix command in a terminal window:
stty –f /dev/PORTNAME
-> example -> stty -f
/dev/tty.USA28X3d1P1.1
which will display the device status. The first thing it tells
you is the speed. It most likely will be 9600. If it is not
you need to set it, also
by using the stty command (see the unix “man” or “info” pages [e.g.,
terminal command: man
stty] for details of syntax and use).
Note: UMBRAPHILE is pretty transparent to most other
flags and switches you could set – so I wouldn't mess with those unless
you are having a
communications problem with the USB-to-Serial port adapter. If
you are having a problem, UMBRAPHILE (X or Classic) wants it's I/O port
set up as: 9600 baud, ASCII half duplex, no parity, 1 stop bit, 8 data
bits, no handshaking, and ASCII character translation. In
UMBRAPHILE Classic (2006 B) you can set those within the Application.
With UMBRAPHILEX you ned to reset those port parameters with the unix
stty command (if needed).
3. Interrupting an Exposure
Sequence In Progress and "Unhiding" the UMBRAPHILEX Menu.
To interrupt an UMBRAPHILEX automated eclipse imaging
controller, or the intervelometer* sequence in progress,
progress you have to:
(a) click anywhere in the main UMBRAPHILEX window
and then
(b) select INTERRUPT from the Umbaphile menu OR hit "Command" +
"." twice.
In either case you must FIRST click in the UMBRAPHILEX window to "bring
it forward".
This may
seem a bit cumbersome; but is done so you won't accidentally interrupt
an exposure sequence in progress with a simple mis-stroked key (which
could be quite disastrous during totality!).
Can't find the UMBRAPHILEX menu? The
Umbraphile menu will be "hidden" (removed from the menu bar), unless
you bring the main UMBRAPHILEX window "forward" by clicking on
it. If you are using UMBRAPHILE and don't see its menu, that is
why – just click in the main window.
3. New Camera Control
Parameter (entered in data file): DEPULSE.
4. There is a new camera control parameter in the Umbraphile data file
in the Camera Controller section called DELPULSE. In UMBRAPHLEX
this replaces the ZEROPULSE parameter (still needed in the "Classic"
version of Umbraphile, but ignored in UMBRAPHILEX) . You will still see
in the template
01AUG2008 Umbraphile data file zipped up with the Intel MacOS X
application (or separately downloaded). DELPULSE, like some of
the other camera-specific
parameters may need some tuning, but generally should be about 10% less
than the MINCMD value as documented on the "classic" umbraphile web
page.
That's it except to say thanks to Simon Marsden of Micro APL Ltd. For
his help in enabling a critical piece of the S/W interface needed
within the UMBRAPHILE code.
Cheers,
Glenn Schneider
gschneider@mac.com, gschneider@as.arizona.edu